Named pipes and Progress
Figure 8–2 shows typical data exchanges between a Progress 4GL application and an external application using named pipes.
A OpenEdge database client accesses named pipes in the same manner as any input or output file. Typically, the OpenEdge database client acts as a 4GL server, receiving 4GL requests from a non-OpenEdge UNIX or Windows application through an input pipe, executing the 4GL statements, and returning the results to the UNIX or Windows application through an output pipe. Chapter 11, "Named Pipes," emphasizes this type of client/server interaction with Progress using named pipes.